Appendix C
(normative)
Open Issues Known Omissions
There are currently no test cases defined for the following areas:
Calendar test cases do not include attachments
Day Event test cases are not considered complete. Issues such as time transparency for all-day events. For example, should all-day events block time (free/busy handling)? Is the meaning preserved between device & server? A consensus within the industry needs to be reached before these tests can be considered complete.
Recurrence tests are not considered complete: Frequencies less than a day (secondly, minutely, hourly), various until/count/interval combinations, various
BYXXXrepeat patterns,WKST, limited coverage of combinations of repeat patterns, limited coverage of exception combinations and repeat modification/deletion. If iCalendar test data is supplied, verify that recurrence property parameters can be specified in any order. A consensus within the industry on what the minimal level of support should be on a mobile device is required to complete a concrete set of tests.Minimal Alarms/Meeting reminders and the handling of alarms on the device are provided but a proper consensus on how to have reminders specified that make sense for the environment they are going off in needs to be reached.
Tests covering meetings that start, end, or cross over the shift between standard and daylight savings are not covered. Consensus on what should be the expected behaviour is needed.
Various scheduling operations such as delegation, meeting cancellation, and meeting reschedules are not covered. Once Scheduling capabilities are more prevalent on mobile devices additional test cases should be added.
Repeating Tasks or Task Assignments are not covered. When such support becomes more widespread on mobile devices additional test cases should be added.
Character Encoding IOP issues. For example: Shift JIS support & confusion with encoding Yen symbol/backslash characters, base64/quoted printable encodings, line folding, UTF-8 support